meta: update stalebot#4379
Conversation
|
It's extremely important that these are tested before merge. I didn't do a full test, as I don't have the resources, but they should get one. |
|
60 days seem to be very aggressive to me. 180 days looks reasonable. |
|
Previous discussion on this #4270 |
I feel like, if nothing has happened with your issue in 60 days, chances are nothing will occur with it. I think 180 is too long, maybe 90? |
|
@redyetidev - given:
it is possible that some volunteer get some time after one or two months and decides to make spend some quality time to help with a number of issues. I do that occasionally. |
|
I'm happy with changing it to 180 for now, if you'd like. |
|
I'll squash and merge, etc, later today |
|
I deleted the second file as I feel it's an issue for a different PR. If you'd like me to squash LMK. |
|
BTW, @gireeshpunathil, This PR also upped the operation count to 500, which matches the Node.js repo, and will make the bot more effective. |
|
Squashed |
Updates the stalebot with a shorter stale-time, more detailed message, and uses v9.0.0.